chore: standardize worktree location on .claude/worktrees/#201
Merged
Conversation
Align all worktree signals on the path Claude Code's native EnterWorktree tool actually writes to. Previously .gitignore ignored a root-level .worktrees/ that the native tool never used, while worktrees landed in the non-ignored .claude/worktrees/ — producing recurring confusion and stray untracked .claude/ noise. - .gitignore: ignore .claude/worktrees/ (narrow — rest of .claude/ stays tracked) instead of the unused .worktrees/ - CLAUDE.md: declare .claude/worktrees/ as the canonical, cross-repo worktree location so the highest-priority signal is unambiguous Cross-repo: platform agent concurs; platform migrates from its .worktrees/-via-symlink bridge to match, pending Mike's direct confirmation. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
Deploying docs with
|
| Latest commit: |
e7a4e89
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://42a4baec.docs-4n7.pages.dev |
| Branch Preview URL: | https://preview.docs-4n7.pages.dev |
|
🚀 Preview Deployment Update ✅ This PR has been successfully merged into the preview branch. The preview environment will update shortly at: https://docs.preview.trakrf.id |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Settle the recurring "where do worktrees go?" confusion by aligning every signal on the one path Claude Code's native worktree tool actually writes to:
.claude/worktrees/.Why
The native
EnterWorktreetool is hardcoded to create worktrees under.claude/worktrees/and exposes no location knob (onlyworktree.baseRef). But the repo's signals pointed elsewhere:.gitignore.worktrees/.worktrees/at root.claude/worktrees/?? .claude/noise ingit statusThe superpowers
using-git-worktreesskill defaults to.worktrees/only as a no-native-tool fallback — which never fires in this harness because the native tool always exists. So matching the tool is correct.Changes
.gitignore: ignore.claude/worktrees/(narrow — the rest of.claude/stays tracked, per the standing decision not to ignore all of.claude/) instead of the unused.worktrees/.CLAUDE.md: add a## Worktreessection declaring.claude/worktrees/canonical across all trakrf repos — the highest-priority signal the skill checks, so future agents have no ambiguity..worktrees/dir (filesystem cleanup, was gitignored).Cross-repo consistency
The
platformagent concurs (.claude/worktrees/is cleaner; the.worktrees/-via-symlink bridge is a footgun) and will migrate platform to match — pending Mike's direct confirmation of the convention change.🤖 Generated with Claude Code